Ui Lead Developer - W2 Requirement

Company: Lorvenk Technologies

Location: Charlotte, NC

Posted on: July 16

Role: UI Lead Developer

Exp: 11+Yrs

Loc: Charlotte, NC (Onsite)

Visa: H1B, EAD, USC

Type: W2

Were looking for recent experience with pure React+Typescript, with best practices

from React 18 (like no CLASSical components or CLASSical HOCs). Frameworks on

top of React (like NextJS) arent what were looking for.

No frameworks. NextJS and other frameworks on top or React are more a minus, than

plus.

Candidate should have recent experience with Redux and Redux Sagas specifically

(not alternatives like Zustand and other state management libraries). It can be ReduxJS

Toolkit (also known as RTK), but I will get deep into what it solves and why, and how it

works. Were not leveraging RTK too much in our code base. Understanding of what

Sagas can do besides sending API requests is a must.

Candidate should have recent experience working on long term projects with at least

12-14 months on a single project/app, so that we could have candidates with correct

mind set about how requirements evolve with time, and how we can make ourselves

ready to adapt to changing requirements. Small product/company with 18 months

contract is good fit. 6 months for huge international corporation is not. Long term

contract with considerable degree of engineering ownership and freedom for huge

international corporation is the best, but you cant have everything, and so `long term

with ownership and freedom` is preferred over huge corporation.

Candidate should have experience with working/creating/maintaining basic components

(buttons, dropdowns, layouts, etc) without any 3rd party library such as Chakra, MUI,

Antd, or others. They ought to be experienced with styles-in-JS pattern using either

styled-components, or @emotion/styled. Preferably including advanced patterns like

custom themes, theme mapping and wrappers, mobile responsive components, things

like these.

Experience with latest data routing from react-router-dom is a plus, but not a deal

breaker

Experience with mono repositories will be a plus (NX workspace is a huge plus), but not

a deal breaker

When Im sure theyre familiar enough with things listed above, I WILL ask about

architecture layering, its why and how.

Practiced ownership over their engineering decisions, and being exposed to the

autonomy and decision making outside of what CSS style to apply here